Image acquisition and management

ABSTRACT

A reference image of one or more objects is displayed on the display of a mobile device in a manner that allows a user of the mobile device to simultaneously view the reference image and a preview image of the one or more objects currently in a field of view of a camera of the mobile device. An indication is provided to the user of the mobile device whether the camera of the mobile device is currently located within a specified amount of a distance at which the reference image was acquired. In response to a user request, the camera acquires a second image of the one or more objects and optionally a distance between the camera and the one or more objects at the time the second image was acquired is recorded. An image management application provides various functionalities for accessing and managing image sequences.

RELATED APPLICATION DATA AND CLAIM OF PRIORITY

This application is related to U.S. patent application Ser. No. 14/543,712 (Attorney Docket No. 49986-0811) entitled IMAGE ACQUISITION AND MANAGEMENT, filed Nov. 17, 2014, U.S. patent application Ser. No. 14/543,725 (Attorney Docket No. 49986-0817) entitled IMAGE ACQUISITION AND MANAGEMENT, filed Nov. 17, 2014 and U.S. patent application Ser. No. 14/641,264 (Attorney Docket No. 49986-0818) entitled IMAGE ACQUISITION AND MANAGEMENT, filed Mar. 6, 2015, the contents all of which are incorporated by reference in their entirety for all purposes as if fully set forth herein.

FIELD OF THE INVENTION

Embodiments relate generally to acquiring and managing images.

BACKGROUND

The approaches described in this section are approaches that could be pursued, but not necessarily approaches that have been previously conceived or pursued. Therefore, unless otherwise indicated, it should not be assumed that any of the approaches described in this section qualify as prior art merely by virtue of their inclusion in this section.

An increasing number of mobile devices, such as smartphones and tablet computers, are equipped with cameras. This makes them increasingly valuable to individuals and businesses. One of the issues with mobile devices that include cameras is that when multiple images of the same object are captured over time, it can be difficult to analyze changes in the objects because the images may not have been captured at the same distance or angle, in the same lighting conditions, or using the same camera settings. In addition, different mobile devices may be used to acquire subsequent images in a sequence. Further, multiple personnel having different skill levels and training may be operating the mobile device(s). Thus, apparent changes in objects captured in a sequence of images may be attributable to factors other than actual changes in the objects.

SUMMARY

A mobile device includes a camera, a display, one or more processors, one or more memories communicatively coupled to the one or more processors and an image acquisition application executing on the mobile device. The image acquisition application is configured to receive an identification of a reference image of one or more objects and automatically adjust one or more camera settings based upon the reference image of the one or more objects, wherein the one or more camera settings after the adjustment are different than the one or more settings prior to the adjustment.

BRIEF DESCRIPTION OF THE DRAWINGS

In the figures of the accompanying drawings like reference numerals refer to similar elements.

FIG. 1 is a block diagram that depicts an arrangement 100 for acquiring and managing images.

FIG. 2A is a flow diagram that depicts an approach for a mobile device to acquire images using a reference image as a background image and a distance at which the reference image was acquired.

FIG. 2B is a flow diagram that depicts an approach for a mobile device to acquire images using a distance at which a reference image was acquired.

FIG. 2C is a flow diagram that depicts an approach for using intensity of acquired images to provide more consistent lighting conditions.

FIG. 2D is a flow diagram that depicts an approach for automatically acquiring one or more subsequent images that are most similar to a reference image.

FIG. 2E is a flow diagram that depicts an approach for automatically acquiring a composite image.

FIG. 2F is a flow diagram that depicts an approach for adjusting a tonal value in a subsequent image to make the subsequent image more visually similar to a reference image.

FIG. 2G is a flow diagram that depicts an approach for creating a movie from a historical sequence of images.

FIG. 3A depicts an example reference image that includes one or more objects that are represented by different shapes.

FIG. 3B depicts a distance at which a reference image was acquired.

FIG. 3C depicts a preview image displayed on a mobile device display.

FIG. 3D depicts a mobile device that has been positioned and oriented so that the one or more objects in a reference image and one or more preview images overlap.

FIG. 4A depicts top-level information that includes a patient identification field (“ID Scan”), an anatomy identification field (“Anatomy ID”), a department field (“Department”), a status field (“Status”) and a registered nurse name (“RN-Name”).

FIG. 4B depicts that a user has used one or more controls (graphical or physical) on a mobile device to navigate to the department field.

FIG. 4C depicts the department options available to the user after selecting the department field and that the user has navigated to the Dermatology department option.

FIG. 4D depicts a graphical user interface allows the user to specify a wristband setting, a body part, a wound type and an indication of the seriousness of the injury.

FIG. 5A depicts a table of example types of memorandum data.

FIG. 5B is a table that depicts a textual representation of image data 552 that includes embedded audio data.

FIG. 6A depicts an example login screen that queries a user for user credentials that include a user login ID and password.

FIG. 6B depicts an example dashboard screen that provides access to various functionality for managing image data.

FIG. 6C depicts an example Approval Queue screen, or work queue, that allows a user to view and approve or reject images.

FIG. 6D depicts an example Rejected Image Processing screen that allows a user to view and update information for rejected images.

FIG. 7A is a table that depicts an example patient database, where each row of the table corresponds to a patient and specifies an identifier, a date of birth (DOB), a gender, an ID list, a social security number (SSN), a sending facility, a family name, a first (given) name and another given (middle) name.

FIG. 7B is a table that depicts an example patient database schema.

FIG. 8 depicts an example historical view screen generated by an image management application.

FIG. 9 depicts another example historical view screen generated by an image management application.

FIG. 10 is a block diagram that depicts an example computer system upon which embodiments may be implemented.

DETAILED DESCRIPTION

In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments. It will be apparent, however, to one skilled in the art that the embodiments may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to avoid unnecessarily obscuring the embodiments.

I. OVERVIEW

II. SYSTEM ARCHITECTURE

-   -   A. Mobile Device     -   B. Application Server

III. ACQUIRING IMAGES USING A REFERENCE IMAGE

-   -   A. Distance     -   B. Changing Camera Settings     -   C. Intensity Adjustment     -   D. Automatic Image Selection     -   E. Composite Images

IV. MEMO AND AUDIO DATA

V. IMAGE DATA MANAGEMENT

VI. HISTORICAL VIEWS

VII. POST-ACQUISITION PROCESSING

-   -   Tonal Value Adjustments     -   B. Creating Movies From Historical Images

VIII. IMPLEMENTATION MECHANISMS

I. Overview

An approach is provided for acquiring and managing images. According to the approach, a reference image of one or more objects is displayed on the display of a mobile device in a manner that allows a user of the mobile device to simultaneously view the reference image and a preview image of the one or more objects currently in a field of view of a camera of the mobile device. For example, the reference image may be displayed on the display of the mobile device at a different brightness level, color, or with special effects, relative to the preview image. An indication is provided to the user of the mobile device whether the camera of the mobile device is currently located within a specified amount of a distance at which the reference image was acquired. For example, a visual or audible indication may indicate whether the camera of the mobile device is too close, too far away, or within a specified amount of a distance at which the reference image was acquired. In response to a user request to acquire an image, the camera acquires a second image of the one or more objects and a distance between the camera and the one or more objects at the time the second image was acquired is recorded. The second image and metadata are transmitted to an image management application that is external to the mobile device. For example, the second image and metadata may be transmitted over one or more networks to the image management application executing on an application server. The image management application provides various functionalities for managing images. For example, the image management application may allow a user to review and accept images, reject images and update metadata for images. As another example, the image management application provides a historical view that allows a user to view a sequence of images of one or more objects that were acquired at approximately the same distance and angle, which allows a user to better discern changes over time in the one or more objects.

II. System Architecture

FIG. 1 is a block diagram that depicts an arrangement 100 for acquiring and managing images. Arrangement 100 includes a mobile device 102, an application server 104, an electronic medical record (EMR) system 106, other services 108 and a client device 110, communicatively coupled via a network 112. Arrangement 100 is not limited the particular elements depicted in FIG. 1 and may include fewer or additional elements depending upon a particular implementation. Embodiments are described herein in the context of a single mobile device 102 for purposes of explanation, but the approach is applicable to any number of mobile devices. Network 112 is depicted in FIG. 1 as a single network for purposes of explanation only and network 112 may include any number and type of wired or wireless networks, such as local area networks (LANs), wide area networks (WANs), the Internet, etc. The various elements depicted in FIG. 1 may also communicated with each other via direct communications links.

A. Mobile Device

Mobile device 102 may be any type of mobile device and examples of mobile device 102 include, without limitation, a smart phone, a camera, a tablet computing device, a personal digital assistant or a laptop computer. In the example depicted in FIG. 1, mobile device 102 includes a display 120, a camera 122, a distance detection mechanism 124, a data acquisition component 125, applications 126, including an image acquisition application 128, a microphone 130, a communications interface 132, a power/power management component 134, an operating system 136 and a computing architecture 138 that includes a processor 140 and memory 142, storing image data 144, audio data 146 and metadata 148. Mobile device 102 may include various other components that may vary depending upon a particular implementation and mobile device 102 is not limited to a particular set of components or features. For example, mobile device 102 may include a location component, such as one or more GPS components that is capable of determining a current location of mobile device 102 and generating location data that indicates the current location of mobile device 102. Mobile device 102 may also include manual controls, such as buttons, slides, etc., not depicted in FIG. 1, for performing various functions on mobile device, such as powering on/off or changing the state of mobile device 102 and/or display 120, or for acquiring digital images.

Display 120 may be implemented by any type of display that displays images and information to a user and may also be able to receive user input and embodiments are not limited to any particular implementation of display 120. Mobile device 102 may have any number of displays 120, of similar or varying types, located anywhere on mobile device 102. Camera 122 may be any type of camera and the type of camera may vary depending upon a particular implementation. As with display 120, mobile device 102 may be configured with any number of cameras 122 of similar or varying types, for example, on a front and rear surface of mobile device 102, but embodiments are not limited to any number or type of camera 122.

Distance detection mechanism 124 is configured to detect a distance between the camera 122 on mobile device 102 and one or more objects within the field of view of the camera 122. Example implementations of distance detection mechanism may be based upon, without limitation, infra-red, laser, radar, or other technologies that use electromagnetic radiation. Distance may be determined directly using the distance detection mechanism 124, or distance may be determined from image data. For example, the distance from the camera 122 to one or more objects on the ground and in the field of view of the camera 122 may be calculated based upon a height of the camera 122 and a current angle of the camera 122 with respect to the ground. For example, given a height (h) of the camera 122 and an acute angle (a) between the vertical and a line of sight to the one or more objects, the distance (d) may be calculated as follows: d=h*tan (a). As another example, if one or more dimensions of the one or more objects are known, the distance between the camera 122 and the one or more objects may be determined based upon a pixel analysis of the one or more objects for which the one or more dimensions are known.

Data acquisition component 125 may comprise hardware subcomponents, programmable subcomponents, or both. For example, data acquisition component 125 may include one or more cameras, scanners, memory units or other data storage units, buffers and code instructions for acquiring, storing and transmitting data, or any combination thereof. Data acquisition component 125 may be configured with a Wi-Fi interface and a barcode reader. The Wi-Fi interface may be used to transmit information to and from the data acquisition component 125. The barcode reader may be used to scan or otherwise acquire a code, such as a point of sale (POS) code displayed on an item.

Microphone 130 is configured to detect audio and in combination with other elements, may store audio data that represents audio detected by microphone 130. Communications interface 132 may include computer hardware, software, or any combination of computer hardware and software to provide wired and/or wireless communications links between mobile device 102 and other devices and/or networks. The particular components for communications interface 132 may vary depending upon a particular implementation and embodiments are not limited to any particular implementation of communications interface 132. Power/power management component 134 may include any number of components that provide and manage power for mobile device 102. For example, power/power management component 134 may include one or more batteries and supporting computer hardware and/or software to provide and manage power for mobile device 102.

Computing architecture 138 may include various elements that may vary depending upon a particular implementation and mobile device 102 is not limited to any particular computing architecture 138. In the example depicted in FIG. 1, computing architecture includes a processor 108 and a memory 142. Processor 108 may be any number and types of processors and memory 142 may be any number and types of memories, including volatile memory and non-volatile memory, which may vary depending upon a particular implementation. Computing architecture 138 may include additional hardware, firmware and software elements that may vary depending upon a particular implementation. In the example depicted in FIG. 1 memory 142 stores image data 144, audio data 146 and metadata 148, as described in more detail hereinafter, but memory 142 may store additional data depending upon a particular implementation.

Operating system 136 executes on computing architecture 138 and may be any type of operating system that may vary depending upon a particular implementation and embodiments are not limited to any particular implementation of operating system 136. Operating system 136 may include multiple operating systems of varying types, depending upon a particular implementation. Applications 126 may be any number and types of applications that execute on computing architecture 138 and operating system 136. Applications 126 may access components in mobile device 102, such as display 120, camera 122, distance detection mechanism 124, computing architecture 138, microphone 130, communications interface 132, power/power management component 134 and other components not depicted in FIG. 1, via one or more application program interfaces (APIs) for operating system 136.

Applications 126 may provide various functionalities that may vary depending upon a particular application and embodiments are not limited to applications 126 providing any particular functionality. Common non-limiting examples of applications 126 include social media applications, navigation applications, telephony, email and messaging applications, and Web service applications. In the example depicted in FIG. 1, applications 126 include an image acquisition application 128 that provides various functionalities for acquiring images. Example functionality includes allowing a user to acquire images via camera 122 while a reference image is displayed as a background image. In this example, the image acquisition application 128 is also configured to provide an indication to a user, e.g., a visual or audible indication, to indicate whether the camera 122 of the mobile device 102 is too close, too far away, or within a specified amount of a distance at which the reference image was acquired. Other example functionality includes acquiring metadata, memorandum data and/or audio data that corresponds to the acquired images, and transmitting this information with the acquired images to an image management application that is external to the mobile device 102. These and other example functionalities of image acquisition application 128 are described in more detail hereinafter. Image acquisition application 128 may be implemented in computer hardware, computer software, or any combination of computer hardware and software.

B. Application Server

In the example depicted in FIG. 1, application server 104 includes a data receiver 160, a user interface 162, an image management application 164, a transcription application 166 and storage 168 that includes image data 170, audio data 172 and metadata 174. Application server 104 may include various other components that may vary depending upon a particular implementation and application server 104 is not limited to a particular set of components or features. Application server 104 may include various hardware and software components that may vary depending upon a particular implementation and application server 104 is not limited to any particular hardware and software components.

Data receiver 160 is configured to receive data from mobile device 102 and may do so using various communication protocols and from various media. Example protocols include, without limitation, the File Transfer Protocol (FTP), the Telnet Protocol, the Transmission Control Protocol (TCP), the TCP/Internet Protocol (TCP/IP), the Hypertext Transfer Protocol (HTTP), the Simple Mail Transfer Protocol (SMTP), or any other data communications protocol. Data receiver 118 may be configured to read data from an FTP folder, an email folder, a Web server, a remote media such as a memory stick, or any other media. Data receiver 160 may include corresponding elements to support these transport methods. For example, data receiver 160 may include, or interact with, an FTP server that processes requests from an FTP client on mobile device 102. As another example, data receiver 160 may include, or interact with, an email client for retrieving emails from an email server on mobile device 102 or external to mobile device 102. As yet another example, data receiver 160 may include, or interact with, a Web server that responds to requests from an http client on mobile device 102. Data interface 160 is further configured to support the transmission of data from application server 104 to other devices and processes, for example, EMR system 106, other services 108 and client device 110.

User interface 160 provides a mechanism for a user, such as an administrator, to access application server 104 and data stored on storage 168, as described in more detail hereinafter. User interface 160 may be implemented as an API for application server 104. Alternatively, user interface 160 may be implemented by other mechanisms. For example, user interface 160 may be implemented as a Web server that serves Web pages to provide a user interface for application server 104.

Image management application 164 provides functionality for managing images received from mobile device 102 and stored in storage 168. Example functionality includes reviewing images, accepting images, rejecting images, processing images, for example to improve blurriness or otherwise enhance the quality of images, crop or rotate images, etc., as well as update metadata for images. Example functionality also includes providing a historical view of a sequence of images of one or more objects, where the images in the sequence were acquired using a reference image as a background image and at approximately the same distance from the one or more objects. According to one embodiment, image management application 164 provides a graphical user interface to allow user access to the aforementioned functionality. The graphical user interface may be provided by application software on client device 110, application software on application server 104, or any combination of application software on client device 110 and application server 104. As one example, the graphical user interface may be implemented by one or more Web pages generated on application server 104 and provided to client device 110. Image management application 164 may be implemented in computer hardware, computer software, or any combination of computer hardware and software. For example, image management application 164 may be implemented as an application, e.g., a Web application, executing on application server 104.

Transcription application 166 processes audio data acquired by mobile device 102 and generates a textual transcription. The textual transcription may be represented by data in any format that may vary depending upon a particular implementation. Storage 168 may include any type of storage, such as volatile memory and/or non-volatile memory. Data interface 160 is configured to provide image and/or video data and identification data to EMR system 106, other services 108 and client device 110. Data interface 160 transmits the data to EMR system 106, other services 108 and client device 110 using standard techniques or alternatively, data interface 160 may transmit data to EMR system 106, other services 108 and client device 110 in accordance with Application Program Interfaces (APIs) supported by EMR system 106, other services 108 and client device 110. Application server 104 may be implemented as a stand-alone network element, such as a server or intermediary device. Application server 104 may also be implemented on a client device, including mobile device 102.

III. Acquiring Images Using a Reference Image

According to one embodiment, mobile device 102 is configured to acquire image data using a reference image. Various embodiments includes using a reference image as a background image and using a distance at which the reference image was acquired to acquire subsequent images.

A. Distance

According to one embodiment, mobile device 102 is configured to acquire image data using a reference image as a background image and a distance at which the reference image was acquired. FIG. 2A is a flow diagram 200 that depicts an approach for a mobile device to acquire images using a reference image as a background image and a distance at which the reference image was acquired, according to an embodiment. In step 202, a reference image to be used as a reference image is retrieved. The reference image may be retrieved in response to a user invoking the image acquisition application 128 and specifying an image to be used as the reference image. For example, a user may select an icon on display 120 that corresponds to the image acquisition application 128 to invoke the image acquisition application 128 and the user is then queried for an image to be used as a reference image. The user may then select an image to be used as the reference image, or specify a location, e.g., a path, of an image to be used as the reference image. The reference image may originate and be retrieved from any source. For example, the reference image may have been acquired by mobile device 102 via camera 122 and be stored as image data 144 in memory 142, or at a location external to mobile device 102. As another example, the reference image may have been acquired by a device external to mobile device, such as client device 110, a scanner, or other services 108. The reference image data may be any type or format of image data. Example image data formats include, without limitation, raster formats such as JPEG, Exif, TIFF, RAW, GIF, BMP, PNG, PPM, PGM, PBM, PNM, etc., and vector formats such as CGM, SVG, etc. The reference image may have corresponding metadata 148 that describes one or more attributes of the reference image. Example attributes include, without limitation, camera settings used to acquire the reference image, and a distance from the camera used to acquire the reference image to the one or more objects in the reference image. FIG. 3A depicts an example reference image 300 that includes one or more objects that are represented by different shapes.

In step 204, the reference image is displayed on the mobile device as a background image. For example, image acquisition application 128 may cause the reference image to be displayed on display 120 of mobile device 102. FIG. 3B depicts an example mobile device display 302 that may be, for example, display 120 of mobile device 102. In this example, the reference image 300, which includes the one or more objects, is displayed on the mobile device display 302 as a background image in a manner that allows a user of the mobile device to simultaneously view a preview image of the one or more objects currently in a field of view of the camera. This may be accomplished using a wide variety of techniques that may vary depending upon a particular implementation and embodiments are not limited to any particular technique for displaying the reference image as a background image. For example, one or more attribute values for the reference image 300 may be changed. The attribute values may correspond to one or more attributes that affect the way in which the reference image appears on the mobile device display to a user. Example attributes include, without limitation, brightness, color or special effects. The reference image 300 may be displayed on mobile device display 302 using a lower brightness or intensity than would normally be used to display images on mobile device display 302. As another example, the reference image 300 may be displayed using a different color, shading, outline, or any other visual effect that visually identifies the reference image 300 to a user as a background image.

According to one embodiment, a distance at which the reference image was acquired is indicated on the display of the mobile device. For example, as depicted in FIG. 3B, the distance at which the reference image was acquired may be displayed on the mobile device display 302 by “Background distance: 8 ft”, as indicated by reference numeral 304. In this example, the “Current Distance” is the current distance between the mobile device 102 and the one or more objects currently in the field of view of the camera and viewable by a user as a preview image, as described in more detail hereinafter. The background distance and/or the current distance may be indicated by other means that may vary depending upon a particular implementation, and embodiments are not limited to any particular means for indicating the background distance and the current distance. For example, the background distance and current distance may be indicated by symbols, colors, shading and other visual effects on mobile device display 302.

In step 206, one or more preview images are displayed of one or more objects currently in the field of view of the camera. For example, image acquisition application 128 may cause one or more preview images to be acquired and displayed on display 120. In FIG. 3C, a preview image 310 is displayed on the mobile device display 302. Embodiments are described herein in the context of displaying a single preview image 310 for purposes of explanation only and multiple preview images may be displayed, as described in more detail hereafter. According to one embodiment, the preview image 310 is displayed in a manner to be visually discernable by a user from the reference image 300 displayed as a background image. For example, the preview image 310 may be displayed on the mobile device display 302 using normal intensity, brightness, color, shading, outline, other special effects, etc. Displaying the preview image 310 simultaneously with the reference image 300 displayed as a background image allows a user to visually discern any differences between the distance, height and angle at which the reference image was acquired and the distance, height and angle of the preview image currently displayed on the mobile device display 302. For example, differences in distance may be readily discerned from differences in sizes of the one or more objects, represented in FIG. 3C by the triangle, rectangle, oval and circles in both the reference image 300 and the preview image 310. Differences in angle may be readily discerned when the one or more objects in the reference image 300 and the preview image 310 are three dimensional objects. This allows a user to move and/or orient the mobile device 102 so that the one or more objects depicted in the preview image 310 overlap, or are aligned with, the one or more objects depicted in the reference image 300. Furthermore, successive preview images 310 may be displayed on mobile device display 302, for example on a continuous basis, to allow a user to move and/or reorient the mobile device 102 so that the distance, height and angle of the one or more objects in the reference image 300 and the one or more preview images 310 are at least substantially the same. For example, as depicted in FIG. 3D, the mobile device 102 has been positioned and oriented so that the one or more objects in the reference image 300 and the one or more preview images overlap, indicating that the distance, height and angle of the one or more objects in the reference image 300 and the one or more preview images 310 are at least substantially the same.

In step 208, a determination is made of a current distance between the mobile device and the one or more objects currently in the field of view of the camera. For example, image acquisition application 128 may cause the distance detection mechanism to measure a current distance between the mobile device 102 and the one or more objects in the field of view of the camera 122. This may include the use of reference objects or markers in the field of view of the camera 122. As another example, a current distance between the mobile device 102 and the one or more objects in the field of view of the camera 122 may be determined using a GPS component in mobile device 102 and a known location of the one or more objects. In this example, the GPS coordinates of the mobile device 102 may be compared to the GPS coordinates of the one or more objects to determine the current distance between the mobile device 102 and the one or more objects in the field of view of the camera 122.

In step 210, an indication is provided to a user of the mobile device whether the current distance is within a specified amount of the distance at which the reference image was acquired. For example, the image acquisition application 128 may compare the current distance between the mobile device 102 and the one or more objects, as determined in step 208, to the distance at which the reference image was acquired. The result of this comparison may be indicated to a user of the mobile device 102 in a wide variety of ways that may vary depending upon a particular implementation and embodiments are not limited to any particular manner of notification. For example, the image acquisition application 128 may visually indicate on the display 120 whether the current distance is within a specified amount of the distance at which the reference image was acquired. This may include, for example, displaying one or more icons on display 120 and/or changing one or more visual attributes of icons displayed on display 120. As one example, icon 306 may be displayed in red when the current distance is not within the specified amount of the distance at which the reference image was acquired, displayed in yellow when the current distance is close to being within the specified amount of the distance at which the reference image was acquired and displayed in green when the current distance is within the specified amount of the distance at which the reference image was acquired. As another example, an icon, such as a circle may be displayed and the diameter reduced as the current distance approaches the specified amount of the distance at which the reference image was acquired. The diameter of the circle may increase as the difference between the current distance and distance at which the reference image was acquired increases, indicating that the mobile device 102 is getting farther away from the distance at which the reference image was acquired. As another example, different icons or symbols may be displayed to indicate whether the current distance is within the specified amount of the distance at which the reference image was acquired. As one example, a rectangle may be displayed when the mobile device 102 is beyond a specified distance from the distance at which the reference image was acquired and then changed to a circle as the mobile device 102 approaches the distance at which the reference image was acquired.

Image acquisition application 128 may audibly indicate whether the current distance is within a specified amount of the distance at which the reference image was acquired, for example, by generating different sounds. As one example, the mobile device 102 may generate a sequence of sounds, and the amount of time between each sound is decreased as the mobile device approaches the distance at which the reference image was acquired. The current distance between the mobile device 102 and the one or more objects in the field of view of the camera 122 may also be displayed on the display, for example, as depicted in FIGS. 3C and 3D. In this example, the current distance has changed from 9.5 ft to 8.2 ft as the user moved and/or reoriented the mobile device 102, to be closer to the 8.0 ft at which the reference image was acquired.

In step 212, a second image of the one or more objects is acquired in response to a user request. For example, in response to a user selection of a button 308, the second image of the one or more objects that are currently in the field of view is acquired. Metadata is also generated for the second image and may specify, for example, camera parameter values used to acquire the second image, and a timestamp or other data, such as a sequence identifier, that indicates a sequence in which images were acquired. According to one embodiment, the metadata for the second image includes a reference to the reference image so that the reference image and the second image can be displayed together, as described in more detail hereinafter. The reference may be in any form and may vary depending upon a particular implementation. For example, the reference may include the name or identifier of the reference image. The metadata for the reference image may also be updated to include a reference to the second image.

According to one embodiment, camera settings values used to acquire the reference image are also used to acquire the second image. This ensures, for example, that the same camera settings, such as focus, aperture, exposure time, etc., are used to acquire both the reference image and the second image. This reduces the likelihood that differences in the one or more objects in the sequence of images are attributable to different camera settings used to acquire the images, rather than actual changes in the one or more objects. Camera settings used to acquire an image may be stored in the metadata for the acquired image, for example, in metadata 148, 174.

The current distance may optionally be reacquired and recorded in association with the second image, for example, in the metadata for the second image. Alternatively, the distance at which the reference image was acquired may be used for the second image, since the current distance is within the specified amount of the distance at which the reference image was acquired.

Image data, representing the second image, and optionally the current distance, may be stored locally on mobile device, for example, in memory 142, and/or may be transmitted by mobile device 102 for storage and/or processing on one or more of application server 104, EMR system 106, other services 108 or client device 110. Image data may be transmitted to application server 104, EMR system 106, other services 108 or client device 110 using a wide variety of techniques, for example, via FTP, via email, via http POST commands, or other approaches. The transmission of image data, and the corresponding metadata, may involve the verification of credentials. For example, a user may be queried for credential information that is verified before image data may be transmitted to application server 104, EMR system 106, other services 108 or client device 110. Although the foregoing example is depicted in FIG. 2 and described in the context of acquiring a second image, embodiments are not limited to acquiring a single image using a reference image and any number of subsequent images may be acquired using a reference image as a background image. When more than one subsequent images are acquired using a reference image, the metadata for the subsequent images may include a reference to the reference image and the other subsequent images that were acquired using the reference image. For example, suppose that a second and third image were acquired using the reference image. The metadata for the second image may include a reference to the reference image and to the third image. The metadata for the third image may include a reference to the reference image and the second image. The metadata for the reference image may include no references the second and third images, a reference to the second image, a reference to the third image, or both. The reference data and timestamp data are used to display the reference image and one or more subsequent images acquired using the reference image as a background image as an ordered sequence, as described in more detail hereinafter.

B. Changing Camera Settings

According to one embodiment, camera settings values used to acquire the reference image are also used to acquire subsequent images. This ensures, for example, that the same camera settings, such as zoom, focus, aperture, exposure time, orientation, etc., are used to acquire both the reference image and the second image. This reduces the likelihood that differences in the one or more objects in the sequence of images are attributable to different camera settings used to acquire the images, rather than actual changes in the one or more objects. Camera settings used to acquire an image may be stored in the metadata for the acquired image, for example, in metadata 148, 174, and retrieved and used for subsequent images. For example, suppose that a first set of camera settings is used to acquire the reference image. The first set of camera settings may be stored in association with the reference image, for example in the metadata 148, 174 for the reference image. The first set of camera settings are retrieved from the metadata 148, 174 for the reference image and used to acquire subsequent images. According to one embodiment, the current distance at which the second image was acquired is determined and may be stored in association with the second image, for example, in the metadata for the second image.

According to one embodiment, mobile device 102 is configured to automatically change one or more camera settings to account for differences in the way that images are acquired. The camera settings that are changed may vary depending upon a particular implementation and embodiments are not limited to any particular camera settings. The particular camera settings to be changed may be specified by an administrator, for example during configuration of camera 122 or via image acquisition application 128, or may be specified by an end user of mobile device 102. The particular camera settings used to correct for differences in the way that images are acquired may vary from image to image, or may be the same for a set of subsequent images. Example settings include, without limitation, optical zoom settings, scaling settings and orientation settings. The change in camera settings may affect the way in which subsequent images are acquired and/or may affect the processing of subsequent images after they have been acquired, depending upon the particular device used to acquire the images. For example, changing optical zoom or orientation settings changes the way subsequent images are acquired while changing scaling settings may change the way subsequent images are acquired and/or processed after being acquired. The changing of camera settings may be done automatically, without user notification. Alternatively, a user may be notified that camera settings have been changed and optionally may be given a choice to accept or deny the change in camera settings, e.g., via graphical user interface objects displayed on camera 122.

FIG. 2B is a flow diagram 220 that depicts an approach for a mobile device to acquire images using a distance at which a reference image was acquired. More specifically, the approach includes automatically changing one or more camera settings and/or processing subsequent images, to account for a current distance, at which one or more subsequent images are acquired, being different than the distance at which the reference image was acquired. In step 222, a reference image is selected and a distance at which the reference image was acquired is retrieved. The reference image may be selected by a user via image acquisition application 128. For example, a user may select an icon on display 120 that corresponds to the image acquisition application 128 to invoke the image acquisition application 128 and the user is then queried for an image to be used as a reference image. The user may then select an image to be used as the reference image, or specify a location, e.g., a path, of an image to be used as the reference image. The distance information for the reference image may be stored in the metadata for the reference image, for example, in metadata 148.

In step 224, a preview image may be displayed of one or more objects currently in the field of view of the camera. This step is optional although it may be helpful for users to view a preview of the one or more objects to be captured. Alternatively, a user may choose to use a view finder on mobile device 102. In addition, the reference image may be displayed as a background image on display 120 of mobile device 102 and audio and/or visual indications may be provided to indicate whether the current distance is within a specified distance of the distance at which the reference image was acquired, as previously described herein. Also, the distance at which the reference image was acquired may be indicated on the display of the mobile device, as previously described herein.

In step 226, a user request is received to acquire a second image of the one or more objects. For example, in response to a user selection of a button 308, the second image of the one or more objects that are currently in the field of view is acquired. Metadata is also generated for the second image and may specify, for example, camera parameter values used to acquire the second image, and a timestamp or other data, such as a sequence identifier, that indicates a sequence in which images were acquired. According to one embodiment, the metadata for the second image includes a reference to the reference image so that the reference image and the second image can be displayed together, as described in more detail hereinafter. The reference may be in any form and may vary depending upon a particular implementation. For example, the reference may include the name or identifier of the reference image. The metadata for the reference image may also be updated to include a reference to the second image.

In step 228, a current distance between the camera and the one or more objects is determined, one or more camera settings are adjusted and the second image is acquired. The current distance between camera 122 and the one or more objects in the field of view of camera 122 may be determined using a wide variety of techniques, as previously described herein. For example, the current distance may be determined using distance detection mechanism 124, with or without reference objects or markers, or a GPS component in mobile device 102. The current distance may also be visually or audibly indicated to the user as previously described herein.

The camera settings adjusted are camera settings that affect image acquisition, for example, lens zoom settings or scaling settings. According to one embodiment, step 228 includes determining a difference between the current distance and the distance at which the reference image was acquired and then adjusting the camera settings based upon the determined difference. For example, if the current distance is determined to be greater than the distance at which the reference image was acquired, then the lens zoom setting may be changed to reduce the current distance camera 122 and the one or more objects in the field of view of camera 122. As another example, a scaling setting may be changed to effectively reduce the current distance camera 122 and the one or more objects in the field of view of camera 122. The second image is then acquired using the adjusted camera settings.

In step 230, the second image may optionally be processed, after being acquired, according to the camera settings used in step 228. For example, the second image may be scaled by camera 122 to account for the difference between the current distance from camera 122 to the one or more objects and the distance at which the reference image was acquired. The processing performed in step 230 may be performed instead of or in addition to the processing performed in step 228. Some types of camera settings are not dependent upon the distance at which the reference image was acquired. For example, orientation is not distance-dependent and according to one embodiment, an orientation setting of camera 122, e.g., landscape, portrait, etc., is changed to the orientation setting that was used to acquire the reference image, as specified in the metadata for the reference image.

Image data, representing the second image, and metadata for the second image may be stored locally on mobile device, for example, in memory 142, and/or may be transmitted by mobile device 102 for storage and/or processing on one or more of application server 104, EMR system 106, other services 108 or client device 110. Image data may be transmitted to application server 104, EMR system 106, other services 108 or client device 110 using a wide variety of techniques, for example, via FTP, via email, via http POST commands, or other approaches. The transmission of image data, and the corresponding metadata, may involve the verification of credentials. For example, a user may be queried for credential information that is verified before image data may be transmitted to application server 104, EMR system 106, other services 108 or client device 110. Although the foregoing example is depicted in FIG. 2B and described in the context of acquiring a second image, embodiments are not limited to acquiring a single image using a reference image and any number of subsequent images may be acquired using a reference image as a background image. When more than one subsequent images are acquired using a reference image, the metadata for the subsequent images may include a reference to the reference image and the other subsequent images that were acquired using the reference image. For example, suppose that a second and third image were acquired using the reference image. The metadata for the second image may include a reference to the reference image and to the third image. The metadata for the third image may include a reference to the reference image and the second image. The metadata for the reference image may include no references the second and third images, a reference to the second image, a reference to the third image, or both. The reference data and timestamp data are used to display the reference image and one or more subsequent images acquired using the reference image as a background image as an ordered sequence, as described in more detail hereinafter.

B. Intensity Adjustment

Images of an object acquired over time may be acquired in different lighting conditions, which may make it more difficult to visually discern changes in the object itself over time. For example, a first (reference) image of an object may be acquired outdoors in natural light and a second image of the object may be acquired a week later either indoors or outdoors in different lighting conditions than when the first image was acquired. The difference in lighting conditions may greatly change the appearance of the two images and make it difficult to visually determine changes in the object captured in each of the two images.

According to one embodiment, the intensity for a reference image is determined and used during the acquisition of subsequent images to provide more consistent lighting conditions. As described in more detail hereinafter, embodiments include notifying a user that the intensity for an acquired image is not within a specified amount of the intensity for a prior image. This informs the user to adjust the current lighting conditions and acquire one or more additional images. This is beneficial, for example, in the medical context where a reference image of a patient is acquired and subsequent images of the patient are acquired in different lighting conditions.

The intensity for an image may be determined from the image itself. For example, one or more regions of an acquired image, or the entire acquired image, may be analyzed to determine the intensity or brightness. The one or more regions may be regions that contain a common object or a reference point to provide a better comparison between images. The analysis may include, for example, determining one or more keypoint values, histograms and/or hash values for the one or more regions.

The intensity for an image may be determined from the metadata for the image. For example, the metadata for the acquired image may be examined to identify the camera settings, such as ISO speed, lens aperture, shutter speed, etc., used to acquire the image. The camera settings may be used to determine the intensity for the acquired image. As one example, an exposure value (EV) may be calculated for an image based upon the shutter speed and f-number.

The intensity for an image may also be determined from external sources. For example, a mobile device may be equipped with a light meter and when an image is acquired, an intensity value may be obtained from the light meter and stored with the image, e.g., in the metadata for the image.

FIG. 2C is a flow diagram 240 that depicts an approach for using intensity of acquired images to provide more consistent lighting conditions. In step 242, a reference image of one or more objects is acquired or retrieved and the intensity for the reference image is determined. As previously described herein, the reference image may be retrieved in response to a user invoking the image acquisition application 128 and specifying an image to be used as the reference image. The reference image may be stored locally on mobile device 102 or at a location external to mobile device 102. Alternatively, a reference image may be acquired using camera 122. The intensity for the reference image may be determined from an analysis of one or more regions of the reference image or from metadata for the reference image, as previously described herein.

In step 244, a user request is received to acquire a second image of the one or more objects. For example, in response to a user selection of a button 308, the second image of the one or more objects that are currently in the field of view is acquired. Metadata is also generated for the second image and may specify, for example, camera parameter values used to acquire the second image, and a timestamp or other data, such as a sequence identifier, that indicates a sequence in which images were acquired.

In step 246, the intensity of the second image is determined. This may be determined using the same technique that was used for the reference image, e.g., by an analysis of one or more regions of the reference image or from metadata for the reference image.

In step 248, the intensity for the second image is compared to the intensity of the reference image and a determination is made whether a threshold is exceeded. For example, the EV for the second image may be compared to the EV for the reference image and if the difference is within a specified threshold, then the intensity for the second image is considered to be the same as the intensity for the reference image. If the difference between the intensity for the second image and the intensity for the reference image exceeds the specified threshold, then the intensity for the second image is considered to be different than the intensity for the reference image. The specified threshold may be configured by an administrator for image acquisition application 128.

In step 250, a user of mobile device 102 is notified that the specified threshold is exceeded. The notification informs the user that the current lighting conditions are sufficiently different than the lighting conditions that existed when the reference image was acquired that the user should acquire another image. The user may choose to delete the current (second) image before acquiring additional images. Alternatively, the current (second) image may be automatically deleted. The notification may be provided in many different ways that may vary depending upon a particular implementation. For example, a message may be displayed on display 120 of mobile device 102 notifying the user that the lighting conditions should be adjusted. The message may indicate to the user how the lighting conditions should be adjusted. For example, if the intensity for the second image is greater than the intensity for the reference image, the message may indicate to the user that the current lighting should be reduced. Similarly, if the intensity for the second image is less than the intensity for the reference image, the message may indicate to the user that the current lighting should be increased. An audible notification may be provided instead of or in addition to the visual notification. The notification may also provide an indication of how much the current lighting should be changed. The process may be repeated as many times as necessary until the intensity of a subsequent image is within the threshold amount of the intensity of the reference image.

According to another embodiment, the intensity for the second image is determined before actually acquiring the second image. This may be accomplished in different ways that may vary depending upon a particular implementation. For example, at the time the user request is received to acquire the second image in step 244, the current camera settings may be used to calculate a current intensity at which the second image will be acquired. As another example, the current intensity may be determined from an external source, such as a light meter, as previously described herein. As yet another example, a preview image may be captured and analyzed to determine the current intensity. The current intensity determined using any of these example approaches may then be used in steps 246-250 and the user notified if the specified threshold is exceeded.

C. Automatic Image Selection

According to one embodiment, mobile device 102 is configured to automatically acquire one or more subsequent images and identify from the one or more subsequent images, one or more particular subsequent images that are most similar to a reference image. The approach generally includes acquiring a plurality of images using different exposure settings, e.g., one or more of an aperture setting, a shutter speed or an ISO setting, and determining one or more images from the plurality of images that best match a reference image. This provides the benefit of simplifying the process of acquiring subsequent images that are similar to a reference image, where the exposure settings for the reference image may not be known or readily available, or where the conditions under which the subsequent images are acquired are different than the conditions under which the reference image was acquired. For example, suppose that medical personnel acquire a first (reference) image of a wound site on a patient and later, other medical personnel wish to acquire additional images of the wound site to compare to the first image. Suppose further that the other personnel are not aware of the lighting conditions and/or exposure settings used to acquire the first image. The current approach allows the other medical personnel to easily acquire additional images that are most similar to the first image and that will be most helpful in evaluating the progress of the wound site, even when the medical personnel are not aware of the lighting conditions or exposure settings used to acquire the reference image, or where different equipment was used to acquire the reference image.

FIG. 2D is a flow diagram 260 that depicts an approach for automatically acquiring one or more subsequent images that are most similar to a reference image. In step 262, a reference image of one or more objects is acquired or retrieved. As previously described herein, the reference image may be retrieved in response to a user invoking the image acquisition application 128 and specifying an image to be used as the reference image. The reference image may be stored locally on mobile device 102 or at a location external to mobile device 102. Alternatively, a reference image may be acquired using camera 122.

In step 264, a user request is received to acquire one or more subsequent images of the one or more objects. For example, the process may be initiated in response to a user selection of a button 308. In this example, button 308 may be labeled or otherwise identified to the user as being associated with the current approach for automatically acquiring one or more subsequent images that are most similar to a reference image of the one or more objects that are currently in the field of view is acquired. For example, button 308 may be accompanied by a label “Acquire Additional Images.” The reference image may be used as a background image on the display 120 of mobile device 102 and/or the distance at which the reference image was acquired may be used to aid the user in acquiring the subsequent images, as previously described herein.

In step 266, one or more subsequent images of the one or more objects are acquired using different exposure settings. The exposure settings used may include one or more of an aperture setting, a shutter speed or an ISO setting. A different combination of exposure settings may be used for each of the subsequent images. The selection of exposure settings used for the subsequent images may be random or may be structured. For example, the exposure settings may be selected to provide a range of exposures from dark to light, to increase the likelihood that one of the subsequent images will at least closely match the reference image.

Alternatively, the selection of exposure settings may be based, at least in part, on one or more exposure settings used to acquire the reference image, if this information is available. The metadata for the reference image may include one or more of the exposure settings used to acquire the reference image and the available exposure settings may be used as a starting point for the subsequent images. For example, the exposure settings used to acquire the subsequent images may be selected to provide exposures that are darker than, similar to, and lighter than the exposure settings used to acquire the reference image.

The number of subsequent images acquired may vary depending upon a particular implementation and embodiments are not limited to any particular number of subsequent images. The computational cost and time required to acquire and compare the subsequent images to the reference image may be a factor in determining the number of subsequent images to acquire. The number of subsequent images may be specified by an end user or alternatively, may be specified by an administrator. For example, after a user has selected button 308 to initiate the process, image acquisition application 128 may provide graphical user interface controls for specifying the number of subsequent images to be acquired and the number of best matches that are to be retained. Alternatively, the number of bets images to be retained may be pre-configured in image acquisition application 128. Image acquisition application 128 may also provide graphical user interface controls for specifying the exposure settings to be used to acquire the subsequent images, should a user desire to specify one or more exposure settings for the subsequent images. For example, the controls may allow a user to specify the number of subsequent images to be acquired, the EV step between subsequent images, and the number of subsequent images to be retained. As another example, the controls may allow a user to specify the number of subsequent images to be acquired, a starting exposure point, and a “coarse” or “fine” setting that will automatically define the EV step between subsequent images. The subsequent images may be acquired using a wide variety of time separation that may vary depending upon a particular implementation. For example, the subsequent images may be acquired in rapid succession, or the subsequent images may be acquired using a specified time spacing. According to one embodiment, metadata is generated and stored for the subsequent images and may specify, for example, the camera settings used to acquire the subsequent images, a timestamp or other data, such as a sequence identifier, that indicates a sequence in which images were acquired, and a reference to the reference image.

In step 268, the one or more subsequent images are compared to the reference image and one or more best matching images are determined. The comparison of the subsequent images to the reference image may be performed using a wide variety of techniques that may vary depending upon a particular implementation and embodiments are not limited to any particular technique. Example techniques include, without limitation, keypoint matching, histogram matching, keypoint+decision tree matching, hash-based or perceptual hash-based (phash) matching, feature-based matching, with or without scaling or subsampling, etc. Thresholds may be used to designate when a match exists between a subsequent image and the reference image. The subsequent images may be scored and ranked and N number of subsequent images selected as the best matching images, where N>=1. The one or more best matching images may be stored on mobile device 102 and/or transmitted to application server 104, so that they may be viewed with the reference image in a historical view, as described in more detail hereinafter. The metadata for the one or more best matching images may specify the reference image to facilitate viewing of the images using the historical view.

According to another embodiment, the one or more subsequent images are all transmitted to application server 104 and the selection of the one or more best matching images is performed at application server 104, as described in more detail hereinafter. This may be useful in situations where it is computationally expensive to determine the best matching images. In addition, image management application 164 may provide a more feature rich and user friendly graphical user interface than mobile device 102.

D. Composite Images

According to one embodiment, mobile device 102 is configured to automatically acquire one or more subsequent images and generate a composite image based upon the one or more subsequent images. The approach generally includes acquiring a plurality of images using different exposure settings, e.g., one or more of an aperture setting, a shutter speed or an ISO setting, and then generating a composite image from one or more images from the plurality of images. Composite images may be beneficial by providing a view of images that is different than when the constituent images are viewed separately. For example, suppose that medical personnel acquire a first (reference) image of a wound site on a patient and later the medical personnel wish to acquire additional images of the wound site to compare to the first image. The current approach allows the medical personnel to acquire and view a composite image with the reference image and/or one or more other individual subsequent images to evaluate the progress of the wound site.

FIG. 2E is a flow diagram 270 that depicts an approach for automatically acquiring a composite image. In step 272, a reference image of one or more objects is acquired or retrieved. As previously described herein, the reference image may be retrieved in response to a user invoking the image acquisition application 128 and specifying an image to be used as the reference image. The reference image may be stored locally on mobile device 102 or at a location external to mobile device 102. Alternatively, a reference image may be acquired using camera 122. The intensity for the reference image may be determined from an analysis of one or more regions of the reference image or from metadata for the reference image, as previously described herein.

In step 274, a user request is received to acquire a composite image of the one or more objects. For example, the process may be initiated in response to a user selection of a button 308. In this example, button 308 may be labeled or otherwise identified to the user as being associated with the current approach for automatically acquiring a composite image of the one or more objects that are currently in the field of view. The reference image may be used as a background image on the display 120 of mobile device 102 and/or the distance at which the reference image was acquired may be used to aid the user in acquiring the subsequent images, as previously described herein.

In step 276, one or more subsequent images of the one or more objects are acquired using different exposure settings. The exposure settings used may include one or more of an aperture setting, a shutter speed or an ISO setting. A different combination of exposure settings may be used for each of the subsequent images. The selection of exposure settings used for the subsequent images may be random or may be structured. For example, the exposure settings may be selected to provide a range of overall exposure from dark to light to increase the likelihood that one of the subsequent images will at least closely match the reference image. The selection of exposure settings may be based, at least in part, on exposure settings used to acquire the reference image, if this information is available. The metadata for the reference image may include one or more of the exposure settings used to acquire the reference image and the available exposure settings may be used as a starting point for the subsequent images. For example, the exposure settings used to acquire the subsequent images may be selected to provide exposures that are darker than, similar to, and lighter than the exposure settings used to acquire the reference image. The number of subsequent images acquired may vary depending upon a particular implementation and embodiments are not limited to any particular number of subsequent images. The computational cost and time required to acquire and compare the subsequent images to the reference image may be a factor in determining the number of subsequent images to acquire. The number of subsequent images may be specified by an end user or alternatively, may be specified by an administrator. For example, image acquisition application 128 may provide graphical user interface controls for specifying the number of subsequent images to be acquired. Image acquisition application 128 may also provide graphical user interface controls for specifying the exposure settings to be used to acquire the subsequent images. For example, the controls may allow a user to specify the number of subsequent images to be acquired and the EV step between subsequent images. As another example, the controls may allow a user to specify the number of subsequent images to be acquired, a starting exposure point, and a “coarse” or “fine” setting that will automatically define the EV step between subsequent images. According to one embodiment, metadata is generated and stored for the subsequent images and may specify, for example, the camera settings used to acquire the subsequent images, a timestamp or other data, such as a sequence identifier, that indicates a sequence in which images were acquired, and a reference to the reference image.

In step 278, a composite image is generated based upon the one or more subsequent images that were acquired. Generation of a composite image may be performed using a wide variety of techniques that may vary depending upon a particular implementation and embodiments are not limited to any particular technique. For example, one or more regions of a first subsequent image may be substituted with corresponding regions from one or more other subsequent images. The one or more regions of the first subsequent image to be replaced may be, for example, regions that include the one or more objects. As another example, entire subsequent images may be layered or blended to provide a composite image. This may be beneficial because different objects in the images may be best viewed with different exposures. For example, suppose that a first object is best viewed in a first subsequent image that was acquired using a first set of exposure settings and that a second object is best viewed in a second subsequent image that was acquired using a second set of exposure settings that are different than the first set of exposure settings. According to one embodiment, a composite image may be generated based upon the first subsequent image and the second subsequent image. This provides the benefit to a user of being able to view, in the composite image, the first object and the second object acquired using different exposure settings, which may be more useful than separately viewing the first and second subsequent images. Any number of subsequent images may be used to generate the composite image and embodiments are not limited to using any particular number of subsequent images. The composite image may be stored on mobile device 102 and/or transmitted to application server 104, so that it may be viewed with the reference image and/or one or more subsequent images, in a historical view, as described in more detail hereinafter. Metadata may be generated for the composite image that specifies the subsequent images used to generate the composite image. The metadata for the composite image may also specify one or more regions of the subsequent images that were used to generate the composite image. The metadata for the composite image may also specify the reference image and/or other subsequent images to facilitate viewing of the images using the historical view.

According to another embodiment, the one or more subsequent images are all transmitted to application server 104 and the generation of a composite image is performed at application server 104, as described in more detail hereinafter. This may be useful in situations where it is computationally expensive to generate the composite image. In addition, image management application 164 may provide a more feature rich and user friendly graphical user interface than mobile device 102.

IV. Memo and Audio Data

According to one embodiment, memorandum (memo) and/or audio data may be acquired to supplement image data. Memorandum data may be automatically acquired by data acquisition component 125, for example, by scanning encoded data associated with the one or more objects in the acquired image. For example, a user of mobile device 102 may scan a bar code or QR code attached to or otherwise associated with the one or more objects, or by scanning a bar code or QR code associated with a patient, e.g., via a patient bracelet or a patient identification card. Memorandum data may be manually specified by a user of mobile device 102, for example, by selecting from one or more specified options, e.g., via pull-down menus or lists, or by entering alphanumeric characters and/or character strings.

FIGS. 4A-D depict an example graphical user interface displayed on display 120 of mobile device 102 that allows a user to specify memorandum data in a medical context. The graphical user interface may be generated, for example, by image acquisition application 128. FIG. 4A depicts top-level information that includes a patient identification field (“ID Scan”), an anatomy identification field (“Anatomy ID”), a department field (“Department”), a status field (“Status”) and a registered nurse name (“RN-Name”). FIG. 4B depicts that a user has used one or more controls (graphical or physical) on mobile device 102 to navigate to the department field. FIG. 4C depicts the department options available to the user after selecting the department field and that the user has navigated to the Dermatology department option. In FIG. 4D, the graphical user interface allows the user to specify a wristband setting, a body part, a wound type and an indication of the seriousness of the injury.

FIG. 5A depicts a table 500 of example types of memorandum data. Although embodiments are described in the context of example types of memorandum data for purposes of explanation, embodiments are not limited to any particular types of memorandum data. In the example table 500 depicted in FIG. 5A, the memorandum data is in the context of images of a human wound site and includes a patient ID, an employee ID, a wound location, an anatomy ID, a wound distance, i.e., a distance between the camera 122 and the wound site, a date, a department, a doctor ID and a status.

Audio data may be acquired, for example, by image acquisition application 128 invoking functionality provided by operating system 136 and/or other applications 126 and microphone 130. The acquisition of audio data may be initiated by user selection of a graphical user interface control or other control on mobile device 102. For example, a user may initiate the acquisition of audio data at or around the time of acquiring one or more images to supplement the one or more images. As described in more detail hereinafter, audio data may be processed by transcription application 166 to provide an alphanumeric representation of the audio data.

Memorandum data and/or audio data may be stored locally on mobile device, for example, in memory 142, and/or may be transmitted by mobile device 102 for storage and/or processing on one or more of application server 104, EMR system 106, other services 108 or client device 110. Memorandum data may be stored as part of metadata 148, 174. Audio data may be stored locally on mobile device 102 as audio data 146 and on application server 104 as audio data 172. In addition, memorandum data and/or audio data may be transmitted separate from or with image data, e.g., as an attachment, embedded, etc.

FIG. 5B is a table 550 that depicts a textual representation of image data 552 that includes embedded audio data 554. In this example, audio data 146, 172 is stored as part of image data 144, 170. Memorandum data may similarly be embedded in image data. The way in which memorandum data and audio data is stored may vary from image data to image data and not all memorandum data and audio data must be stored in the same manner. For example, audio data that corresponds to a reference image may be embedded in the image data for the reference image, while audio data that corresponds to a second image may be stored separate from the image data for the second image.

V. Image Data Management

Various approaches are provided for managing image data. According to one embodiment, image management application 164 provides a user interface for managing image data. The user interface may be implemented, for example, as a Web-based user interface. In this example, a client device, such as client device 110, accesses image management application 164 and the user interface is implemented by one or more Web pages provided by image management application 164 to client device 110.

FIGS. 6A-6D depict an example graphical user interface for managing image data according to an embodiment. The example graphical user interface depicted in FIGS. 6A-6D may be provided by one or more Web pages generated on application server 104 and provided to client device 110. FIG. 6A depicts an example login screen 600 that queries a user for user credentials that include a user login ID and password.

FIG. 6B depicts an example main screen 610, referred to hereinafter as a “dashboard 610”, that provides access to various functionality for managing image data. In the example depicted in FIG. 6B, the dashboard 610 provides access, via graphical user interface controls 612, to logical collections of images referred to hereinafter as “queues,” a user database in the form of a patient database and historical views of images. Although embodiments are described hereinafter in the medical/accident context for purposes of explanation, embodiments are not limited to this context. The queues include an Approval Queue, a Rejected Queue and an Unknown Images Queue that may be accessed via graphical user interface icons 614, 616, 618, respectively. The patient database may be accessed via graphical user interface icon 620.

FIG. 6C depicts an example Approval Queue screen 630, or work queue, that allows a user to view and approve or reject images. Approval Queue screen 630 displays patient information 632 of a patient that corresponds to the displayed image and image information 634 for the displayed image. Approval Queue screen 630 includes controls 636 for managing the displayed image, for example, by expanding (horizontally or vertically) or rotating the displayed image. Controls 638 allow a user to play an audio recording that corresponds to the displayed image. Control 640 allows a user to view an alphanumeric transcription of the audio recording that corresponds to the displayed image. The alphanumeric transcription may be generated by transcription application 166 and displayed to a user in response to a user selection of control 640. Approval Queue screen 630 also includes controls 640, 642 for approving (accepting) or rejecting, respectively, the displayed image. A displayed image might be rejected for a wide variety of reasons that may vary depending upon a particular situation. For example, a user might choose to reject a displayed image because the image is out of focus, the image is otherwise of poor quality, the image does not show the area of interest, or the information associated with the image, such as the patient information 632 or the image information 634 is incomplete.

FIG. 6D depicts an example Rejected Image Processing screen 640 that allows a user to view and update information for rejected images. Rejected Image Processing screen 640 displays patient information 642 of a patient that corresponds to the displayed image and image information 644 for the displayed image. A user may correct or add to the meta data or memorandum data for the displayed image. For example, the user may correct or add to the patient information 642 or the image information 644, e.g., by selecting on a field and manually entering alphanumeric information. Rejected Image Processing screen 640 includes controls 646 for managing the displayed image, for example, by expanding (horizontally or vertically) or rotating the displayed image. Controls 648 allow a user to play an audio recording that corresponds to the displayed image. Control 650 allows a user to view an alphanumeric transcription of the audio recording that corresponds to the displayed image. Rejected Image Processing screen 640 also includes controls 640, 642 for approving (accepting) or rejecting, respectively, the displayed image. For example, after making changes to the displayed image, the patient information 642 or the image information 644, a user may select control 652 to accept the displayed image and cause the displayed image to be added to the Approval queue. Alternatively, a user may maintain the displayed image as rejected by selecting control 654 to cancel.

The unknown images queue accessed via control 618 includes images for which there are incomplete information or other problems, which may occur for a variety of reasons. For example, a particular image may have insufficient metadata to associate the particular image with other images. As another example, a particular image may be determined to not satisfy specified quality criteria, such as sharpness, brightness, etc. Users may perform processing on images in the unknown images queue to provide incomplete information and/or address problems with the images. For example, a user may edit the metadata for a particular image in the unknown images queue to supply missing data for the particular image. As another example, a user may process images in the unknown image queue to address quality issues, such as poor focus, insufficient brightness or color contrast, etc. The images may then be approved and moved to the approval queue or rejected and moved to the rejected queue.

FIG. 7A is a table 700 that depicts an example patient database, where each row of the table 700 corresponds to a patient and specifies an identifier, a date of birth (DOB), a gender, an ID list, a social security number (SSN), a sending facility, a family name, a first (given) name and another given (middle) name. Table 700 may be displayed in response to a user selecting the “Patient Database” control 612. FIG. 7B is a table 750 that depicts an example patient database schema.

VI. Historical Views

According to one embodiment, images are displayed to a user using a historical view. In general, a historical view displays a sequence of images that includes a reference image and one or more other images acquired using the reference image as a background image as described herein.

FIG. 8 depicts an example historical view screen 800 generated by image management application 164 according to an embodiment. A user of client device 110 may access image management application 164 and request access to a historical view of images, for example, by selecting the “Historical View” control 612. In response to this request, image management application 164 may provide access to historical view screen 800. As one non-limiting example, historical view screen 800 may be represented by one or more Web pages provided by image management application 164 to client device 110.

In the example depicted in FIG. 8, historical view screen 800 includes a plurality of graphical user interface objects that include graphical user interface controls 612 that provide access to the dashboard, the image queues and the patient database previously described herein. The historical view screen 800 includes a sequence of images 802-808 of one or more objects selected by a user. When the historical view screen 800 is first displayed, a user may be shown a collection of image sequences, where each image sequence is represented by one or more graphical user interface objects, such as an icon, textual description, thumbnail image or other information. The user selects a graphical user interface object, for example an icon, which corresponds to a particular image sequence of interest, and the images in the particular sequence are displayed.

One or more graphical user interface controls may be provided to arrange the image sequences by a time of information selected, e.g., user identification, organization, event, subject, date/time, etc. The graphical user interface controls may also allow a user to enter particular criteria and have the image sequences that correspond to the particular criteria be displayed. In the example depicted in FIG. 8, the images 802-808 correspond to a particular patient identified in patient information 812. Each image sequence includes the reference image and one or more subsequent images acquired using the reference image, as previously described herein. Note that in the example depicted in FIG. 8, multiple image sequences may be provided for a single user, i.e., a single patient. For example, suppose that a patient sustained injuries on two locations of their body, e.g., an arm and a leg. In this example, one image sequence may correspond to the patient's arm and another image sequence may correspond to the patient's leg.

The images 802-808 include a reference image 802 and three subsequent images acquired using the reference image 802, namely, Image 1 804, Image 2 806 and Image 3 808. In this example, Image 1 804, Image 2 806 and Image 3 808 were acquired using the reference image 802 displayed on the mobile device 102 as a background image, as previously described herein. In addition, the images 802-808 are arranged on historical view screen 800 in chronological order, based upon the timestamp or other associated metadata, starting with the reference image 802, followed by Image 1 804, Image 2 806 and Image 3 808.

Historical view screen 800 also includes controls 810 for managing displayed images 802-808 and information about a user that corresponds to the images 802-808, which in the present example is represented by patient information 812. Image history information 814 displays metadata for images 802-808. In the example depicted in FIG. 8, the metadata includes a date at which each image 802-808 was acquired, but the metadata may include other data about images 802-808, for example, a distance at which the images were acquired 802-808, timestamps, memorandum data, etc. Metadata may also be displayed near or on a displayed image. For example, the timestamp that corresponds to each image 802-808 may be superimposed on, or be displayed adjacent to, each image 802-808.

Controls 816 allow a user to play an audio recording that corresponds to the displayed image and a control 818 allows a user to view an alphanumeric transcription of the audio recording that corresponds to the displayed image.

The historical view approach for displaying a sequence of images that includes a reference image and one or more other images that were acquired using the reference image as a background image and at approximately the same distance is very beneficial to see changes over time in the one or more objects captured in the images. For example, the approach allows medical personnel to view changes over time of a wound or surgical sight. As another example, the approach allows construction personnel to monitor progress of a project, or identify potential problems, such as cracks, improper curing of concrete, etc. As yet another example, the approach allows a user to monitor changes in natural settings, for example, to detect beach or ground erosion.

VII. Post-Acquisition Processing

According to one embodiment, various types of post-acquisition processing are provided for processing sequences of images. FIG. 9 depicts an example historical view screen 900 generated by image management application 164 according to an embodiment. Historical view screen 900 includes controls 902, in the form of check boxes, that allow a user to select one or more images, or all images, in a displayed image sequence, i.e., Image 1 804, Image 2 806 and Image 3 808. Historical view screen 900 also includes controls 904 for performing various types of post-acquisition processing, including controls to determine a best matching image 904, create a composite image 906 and adjust tonal values 908.

Selecting the control for best matching image 904 causes the image management application 164 to determine one or more subsequent images that best match the reference image, as previously described herein in Section III. D. Automatic Image Selection. Selecting the control for create composite image 906 causes the image management application 164 to generate a composite image, as previously described herein in Section III. E. Composite Images. Selecting the control for adjust tonal values 908 causes the image management application 164 to adjust the tonal values for one or more selected images.

A. Tonal Value Adjustments

There may be situations where images acquired subsequent to a reference image have different characteristics than the reference image. For example, the white balance of a reference image may differ from the white balance of a subsequent image if the subsequent image is acquired using a different type of lighting, e.g., incandescent lighting versus natural lighting, than the reference image.

According to one embodiment, adjustments are made to one or more tonal values for one or more subsequent images in a sequence so that the subsequent images are more visually similar to the reference image. The tonal adjustments may include various types of adjustments that may vary depending upon a particular implementation and embodiments are not limited to any particular types of tonal adjustments. Example tonal adjustments include, without limitation, white point adjustment, black point adjustment and mid-tone, i.e., middle-grey, adjustment.

According to one embodiment, adjustment of tonal values may be made using thresholds. For example, a tonal adjustment may be made to a particular subsequent image when the tonal value for the particular subsequent image is not within a specified amount of the tonal value for the reference image. The particular value used for the specified amount to trigger tonal value adjustment may be selected by a user, for example, an administrator. Embodiments are not limited to adjusting a single tonal value for subsequent images and multiple tonal values may be adjusted. For example, more than one of a white point adjustment, a black point adjustment and a middle-grey adjustment may be made in subsequent images.

Making tonal adjustments in subsequent images in a sequence improves the consistency in appearance of images in the sequence, which may make it easier to visually discern changes in one or more objects in the images. For example, having consistent tonal values in a sequence of images of a human wound site can provide more consistence flesh tones, which may allow for a better assessment of changes in the wound site over time. While adjusting the tonal values of images in a sequence may improve or provide more optimal tonal values, this is not required. The resulting image sequence may have sub-optimal tonal values and a corresponding loss of some detail in the images, but may nevertheless be more useful to a user for visually detecting changes over time in the objects captured in the images. This is because after adjusting the tonal values of subsequent images to more closely match the tonal values of the reference image, differences in the images may be attributable to actual changes in the objects of interest, rather than to differences in tonal values in the images caused by differences in lighting conditions.

According to one embodiment, a reference marker, such as a grey card, may be included in the reference image to aid in adjusting tonal values in subsequent images. The reference marker is generally an object of neutral color that reflects a particular amount of light. The reference marker has a known tonal value, e.g., 18% grey, that is used to adjust tonal values in subsequent images. For example, a grey card may be used to establish what is middle-grey in the reference image so that the middle-grey of subsequent images can be adjusted to the middle-grey value of the reference image. The reference marker may be positioned at a specified location in the reference image so that it can be easily located during analysis of the reference image. For example, the reference marker may be position at one of the corners, center or top center of the reference image.

FIG. 2F is a flow diagram 280 that depicts an approach for adjusting a tonal value in a subsequent image to make the subsequent image more visually similar to a reference image. Although the approach is depicted in FIG. 2F and described herein in the context of being performed by image management application 164, the approach may also be performed on a mobile device, for example, by mobile device 102 when the images are acquired.

In step 282, a reference image of one or more objects is retrieved, for example, via image management application 164. The reference image may be stored locally on application server 104 or at a location external to application server 104.

In step 284, the reference image is analyzed to determine a tonal value of the reference image. For example, image management application 164 may analyze a reference image to determine a white point value, a black point value or a middle-grey value of the reference image. As previously described herein, a reference marker, such as a grey card, may be used to establish a particular tonal value, such as middle-grey, in the reference image.

In step 286, a particular subsequent image is selected. For example, a user may select a particular subsequent image using the graphical user interface controls depicted in FIG. 9 that are provided by image management application 164.

In step 288, the particular subsequent image is analyzed to determine a tonal value for the particular subsequent image. For example, if in step 284, the white point value of the reference image was determined, then in step 288, the white point value of the particular subsequent image is determined.

In step 290, a determination is made whether the tonal value for the particular subsequent image is within a specified amount of the tonal value for the reference image. For example, image management application 164 determines whether the white point value for the particular subsequent image is within a specified amount of the white point value for the reference image.

In step 292, one or more tonal values for the particular subsequent image are adjusted, if in step 290, the tonal value for the particular subsequent image is determined to not be within the specified amount of the tonal value for the reference image. For example, suppose that image management application 164 determines that the white point value for the particular subsequent image is not within the specified amount of the white point value for the reference image. In this situation, image management application 164 adjusts the white point value for the particular subsequent image to be within the specified amount of the white point value for the reference image. Although the process is depicted in FIG. 2F and described in the context of adjusting a single tonal value for purposes of explanation, embodiments are not limited to this context and any number of tonal values may be adjusted in subsequent images.

B. Creating Movies from Historical Images

According to one embodiment, image management application 164 provides the capability to generate a time lapsed movie based upon a historical image sequence.

FIG. 2G is a flow diagram 292 that depicts an approach for creating a movie from a historical sequence of images. In step 293, a user request is received to create a movie of a historical sequence of images. For example, a user may select a create movie button 910 in the historical view screen 900 of FIG. 9. In response to the user request, in step 294, a user is queried to select a historical sequence of images. For example, in response to the user selection of the create movie button 910 in the historical view screen 900 of FIG. 9, image management application 164 may cause a navigation window to be generated and displayed that allows the user to select a graphical user interface icon that corresponds to a particular reference image or historical sequence of images that includes a reference image and one or more subsequent images acquired using the reference image, as previously described herein.

In step 295, a movie is generated based upon the selected historical sequence of images. A wide variety of techniques may be used to create a movie based upon a historical sequence of images and embodiments are not limited to any particular approach. The particular technique may vary depending upon the number of images available in the selected historical sequence of images and the desired visual effect. For example, if a historical sequence of images contains a large number of images, e.g., several hundred or thousand, then the movie may be generated with the images compressed into 24 frames per second (fps) with no pause between images. A short (or no) time interval between images generally provides a smooth movie output. As another example, if the historical sequence of images contains relatively few images, e.g., 5-20, then it may be beneficial to include a time interval between images. It may also be beneficial to create a fade between successive images, so that a current image is slowly replaced by a subsequent image. According to one embodiment, image management application 164 provides graphical user interface controls that allow a user to specify a time interval to be used to display the historical sequence of images. This allows a user to view a historical sequence of images at different speeds, which may be beneficial in a wide variety of contexts. Image management application 164 may also be configured to calculate and display to a user an estimated length of the movie, based upon the number of images in the historical sequence of images and the time interval between images specified by the user.

In step 296, controls are provided to a user to allow the movie to be played. For example, image management application 164 may generate and display a graphical user interface that allows the user to play the movie. The controls may also allow a user to rewind, pause, and fast forward the movie. In response to a user selection of one or more of the graphical user interface controls, the movie is played, for example, in a separate window displayed on the graphical user interface generated by the image management application 164.

VII. Implementation Mechanisms

Although the flow diagrams of the present application depict a particular set of steps in a particular order, other implementations may use fewer or more steps, in the same or different order, than those depicted in the figures.

According to one embodiment, the techniques described herein are implemented by one or more special-purpose computing devices. The special-purpose computing devices may be hard-wired to perform the techniques, or may include digital electronic devices such as one or more application-specific integrated circuits (ASICs) or field programmable gate arrays (FPGAs) that are persistently programmed to perform the techniques, or may include one or more general purpose hardware processors programmed to perform the techniques pursuant to program instructions in firmware, memory, other storage, or a combination. Such special-purpose computing devices may also combine custom hard-wired logic, ASICs, or FPGAs with custom programming to accomplish the techniques. The special-purpose computing devices may be desktop computer systems, portable computer systems, handheld devices, networking devices or any other device that incorporates hard-wired and/or program logic to implement the techniques.

FIG. 10 is a block diagram that depicts an example computer system 1000 upon which embodiments may be implemented. Computer system 1000 includes a bus 1002 or other communication mechanism for communicating information, and a processor 1004 coupled with bus 1002 for processing information. Computer system 1000 also includes a main memory 1006, such as a random access memory (RAM) or other dynamic storage device, coupled to bus 1002 for storing information and instructions to be executed by processor 1004. Main memory 1006 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 1004. Computer system 1000 further includes a read only memory (ROM) 1008 or other static storage device coupled to bus 1002 for storing static information and instructions for processor 1004. A storage device 1010, such as a magnetic disk or optical disk, is provided and coupled to bus 1002 for storing information and instructions.

Computer system 1000 may be coupled via bus 1002 to a display 1012, such as a cathode ray tube (CRT), for displaying information to a computer user. Although bus 1002 is illustrated as a single bus, bus 1002 may comprise one or more buses. For example, bus 1002 may include without limitation a control bus by which processor 1004 controls other devices within computer system 1000, an address bus by which processor 1004 specifies memory locations of instructions for execution, or any other type of bus for transferring data or signals between components of computer system 1000.

An input device 1014, including alphanumeric and other keys, is coupled to bus 1002 for communicating information and command selections to processor 1004. Another type of user input device is cursor control 1016, such as a mouse, a trackball, or cursor direction keys for communicating direction information and command selections to processor 1004 and for controlling cursor movement on display 1012. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allows the device to specify positions in a plane.

Computer system 1000 may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic or computer software which, in combination with the computer system, causes or programs computer system 1000 to be a special-purpose machine. According to one embodiment, those techniques are performed by computer system 1000 in response to processor 1004 processing instructions stored in main memory 1006. Such instructions may be read into main memory 1006 from another computer-readable medium, such as storage device 1010. Processing of the instructions contained in main memory 1006 by processor 1004 causes performance of the functionality described herein. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions to implement the embodiments. Thus, embodiments are not limited to any specific combination of hardware circuitry and software.

The term “computer-readable medium” as used herein refers to any medium that participates in providing data that causes a computer to operate in a specific manner. In an embodiment implemented using computer system 1000, various computer-readable media are involved, for example, in providing instructions to processor 1004 for execution. Such a medium may take many forms, including but not limited to, non-volatile media and volatile media. Non-volatile media includes, for example, optical or magnetic disks, such as storage device 1010. Volatile media includes dynamic memory, such as main memory 1006. Common forms of computer-readable media include, without limitation, a floppy disk, a flexible disk, hard disk, magnetic tape, or any other magnetic medium, a CD-ROM, any other optical medium, a RAM, a PROM, and EPROM, a FLASH-EPROM, any other memory chip, memory cartridge or memory stick, or any other medium from which a computer can read.

Various forms of computer-readable media may be involved in storing instructions for processing by processor 1004. For example, the instructions may initially be stored on a storage medium of a remote computer and transmitted to computer system 1000 via one or more communications links. Bus 1002 carries the data to main memory 1006, from which processor 1004 retrieves and processes the instructions. The instructions received by main memory 1006 may optionally be stored on storage device 1010 either before or after processing by processor 1004.

Computer system 1000 also includes a communication interface 1018 coupled to bus 1002. Communication interface 1018 provides a communications coupling to a network link 1020 that is connected to a local network 1022. For example, communication interface 1018 may be a modem to provide a data communication connection to a telephone line. As another example, communication interface 1018 may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, communication interface 1018 sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.

Network link 1020 typically provides data communication through one or more networks to other data devices. For example, network link 1020 may provide a connection through local network 1022 to a host computer 1024 or to data equipment operated by an Internet Service Provider (ISP) 1026. ISP 1026 in turn provides data communication services through the world wide packet data communication network now commonly referred to as the “Internet” 1028. Local network 1022 and Internet 1028 both use electrical, electromagnetic or optical signals that carry digital data streams.

Computer system 1000 can send messages and receive data, including program code, through the network(s), network link 1020 and communication interface 1018. In the Internet example, a server 1030 might transmit a requested code for an application program through Internet 1028, ISP 1026, local network 1022 and communication interface 1018. The received code may be processed by processor 1004 as it is received, and/or stored in storage device 1010, or other non-volatile storage for later execution.

In the foregoing specification, embodiments have been described with reference to numerous specific details that may vary from implementation to implementation. Thus, the sole and exclusive indicator of what is, and is intended by the applicants to be, the invention is the set of claims that issue from this application, in the specific form in which such claims issue, including any subsequent correction. Hence, no limitation, element, property, feature, advantage or attribute that is not expressly recited in a claim should limit the scope of such claim in any way. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense. 

1. A mobile device comprising: a camera; a display; one or more processors; one or more memories communicatively coupled to the one or more processors; and an image acquisition application executing on the mobile device, wherein the image acquisition application is configured to: receive an identification of a reference image of one or more objects, retrieve, for the reference image, metadata that specifies a distance at which the reference image of the one or more objects was acquired, determine a current distance between the camera of the mobile device and the one or more objects, determine a difference between the distance at which the reference image of the one or more objects was acquired and the current distance between the camera of the mobile device and the one or more objects, and automatically adjust one or more camera settings for the camera of the mobile device based upon the difference between the distance at which the reference image of the one or more objects was acquired and the current distance between the camera of the mobile device and the one or more objects, wherein the one or more camera settings after the adjustment are different than the one or more settings prior to the adjustment.
 2. The mobile device of claim 1, wherein an image of the one or more objects acquired using the adjusted one or more camera settings is visually more similar to the reference image of the one or more objects than an image of the one or more objects acquired using the one or more camera settings prior to being adjusted.
 3. The mobile device of claim 1, wherein the one or more camera settings include one or more of a lens zoom setting, an orientation setting, an exposure setting, a resolution setting, or a scaling setting.
 4. The mobile device of claim 1, wherein the image acquisition application is configured to: cause the reference image of the one or more objects to be displayed, on the display of the mobile device, as a background image in a manner that allows a user of the mobile device to simultaneously view one or more preview images of the one or more objects currently in a field of view of the camera, and cause the one or more preview images of the one or more objects currently in a field of view of the camera to be displayed simultaneously with the reference image on the display of the mobile device.
 5. The mobile device of claim 1, wherein the image acquisition application is configured to cause the reference image of one or more objects to be displayed, on the display of the mobile device, as a background image in a manner that allows a user of the mobile device to simultaneously view one or more preview images of the one or more objects currently in a field of view of the camera by changing one or more attribute values for the reference image.
 6. The mobile device of claim 5, wherein the one or more attribute values for the reference image correspond to one or more attributes that include one or more of brightness, color or special effects.
 7. The mobile device of claim 1, wherein the image acquisition application is configured to, in response to a user request, generate and store one or more of memorandum data or audio data.
 8. The mobile device of claim 1, wherein the image acquisition application is configured to, in response to a user request, generate and store an audio recording in the one or more memories of the mobile device.
 9. A one or more non-transitory computer-readable media storing instructions which, when processed by one or more processors, cause: an image acquisition application executing on a mobile device to: receive an identification of a reference image of one or more objects, retrieve, for the reference image, metadata that specifies a distance at which the reference image of the one or more objects was acquired, determine a current distance between the camera of the mobile device and the one or more objects, determine a difference between the distance at which the reference image of the one or more objects was acquired and the current distance between the camera of the mobile device and the one or more objects, and automatically adjust one or more camera settings for the camera of the mobile device based upon the difference between the distance at which the reference image of the one or more objects was acquired and the current distance between the camera of the mobile device and the one or more objects, wherein the one or more camera settings after the adjustment are different than the one or more settings prior to the adjustment.
 10. The one or more non-transitory computer-readable media of claim 9, wherein an image of the one or more objects acquired using the adjusted one or more camera settings is visually more similar to the reference image of the one or more objects than an image of the one or more objects acquired using the one or more camera settings prior to being adjusted.
 11. The one or more non-transitory computer-readable media of claim 9, wherein the one or more camera settings include one or more of a lens zoom setting, an orientation setting, an exposure setting, a resolution setting, or a scaling setting.
 12. The one or more non-transitory computer-readable media of claim 9, further comprising additional instructions which, when processed by the one or more processors, cause the image acquisition application to: cause the reference image of the one or more objects to be displayed, on the display of the mobile device, as a background image in a manner that allows a user of the mobile device to simultaneously view one or more preview images of the one or more objects currently in a field of view of the camera, and cause the one or more preview images of the one or more objects currently in a field of view of the camera to be displayed simultaneously with the reference image on the display of the mobile device.
 13. The one or more non-transitory computer-readable media of claim 9, further comprising additional instructions which, when processed by the one or more processors, cause the image acquisition application to cause the reference image of one or more objects to be displayed, on the display of the mobile device, as a background image in a manner that allows a user of the mobile device to simultaneously view one or more preview images of the one or more objects currently in a field of view of the camera by changing one or more attribute values for the reference image.
 14. The one or more non-transitory computer-readable media of claim 13, wherein the one or more attribute values for the reference image correspond to one or more attributes that include one or more of brightness, color or special effects.
 15. The one or more non-transitory computer-readable media of claim 9, further comprising additional instructions which, when processed by the one or more processors, cause the image acquisition application to, in response to a user request, generate and store one or more of memorandum data or audio data.
 16. The one or more non-transitory computer-readable media of claim 9, further comprising additional instructions which, when processed by the one or more processors, cause the image acquisition application to, in response to a user request, generate and store an audio recording in the one or more memories of the mobile device.
 17. A computer-implemented method comprising: receiving, by an image acquisition application executing on a mobile device, an identification of a reference image of one or more objects, retrieve, for the reference image, metadata that specifies a distance at which the reference image of the one or more objects was acquired, determine a current distance between the camera of the mobile device and the one or more objects, determine a difference between the distance at which the reference image of the one or more objects was acquired and the current distance between the camera of the mobile device and the one or more objects, and automatically adjust one or more camera settings for the camera of the mobile device based upon the difference between the distance at which the reference image of the one or more objects was acquired and the current distance between the camera of the mobile device and the one or more objects, wherein the one or more camera settings after the adjustment are different than the one or more settings prior to the adjustment.
 18. The computer-implemented method of claim 17, wherein an image of the one or more objects acquired using the adjusted one or more camera settings is visually more similar to the reference image of the one or more objects than an image of the one or more objects acquired using the one or more camera settings prior to being adjusted.
 19. The computer-implemented method of claim 17, wherein the one or more camera settings include one or more of a lens zoom setting, an orientation setting, an exposure setting, a resolution setting, or a scaling setting.
 20. The computer-implemented method of claim 17, further comprising: cause, by the image acquisition application executing on the mobile device, the reference image of the one or more objects to be displayed, on the display of the mobile device, as a background image in a manner that allows a user of the mobile device to simultaneously view one or more preview images of the one or more objects currently in a field of view of the camera, and cause, by the image acquisition application executing on the mobile device, the one or more preview images of the one or more objects currently in a field of view of the camera to be displayed simultaneously with the reference image on the display of the mobile device. 